|
mruby 4.0.0
mruby is the lightweight implementation of the Ruby language
|
CRuby3.0 compatible keyword arguments are introduced. Keyword arguments are basically separated from ordinal arguments.
Some configuration macros are available:
We have added several new build configurations in the build_config directory.
Due to improvements in the binary format, mruby binaries are no longer backward compatible. To run the mruby binaries on mruby 3.1, recompile with the mruby 3.1 mrbc.
mruby3.0 removed OP_EXT1, OP_EXT2, OP_EXT3 for operand extension. But the operand size limitations was too tight for real-world application. mruby3.1 reintroduces those extension instructions.
mruby3.1 removed following instructions.
Those instructions are no longer needed by reintroduction of extension instructions.
Those instructions for method calls with variable number of arguments are no longer needed. They are covered by OP_SEND instruction with n=15.
mruby3.1 introduces following new instructions.
Execute obj[int] and obj[int] = value respectively, where obj is string|array|hash.
They are similar to OP_SEND and OP_SENDB respectively. They initialize the R[a] by self first so that we can skip one OP_LOADSELF instruction for each call.
Extracts the character string placed in the pool as a symbol.
Method calling instructions are unified. Now OP_SEND and OP_SENDB (method call with a block) can support both splat arguments and keyword arguments as well.
The brief description of the instructions:
|OP_SEND | BBB | R[a] = R[a].call(Syms[b],R[a+1..n],R[a+n+1],R[a+n+2]..nk) c=n|nk<<4 | |OP_SENDB | BBB | R[a] = R[a].call(Syms[b],R[a+1..n],R[a+n+1..nk],R[a+n+2..nk],&R[a+n+2*nk+2]) c=n|nk<<4 |
Operand C specifies the number of arguments. Lower 4 bits (n) represents the number of ordinal arguments, and higher 4 bits (nk) represents the number of keyword arguments. When n == 15, the method takes arguments packed in an array. When nk == 15, the method takes keyword arguments are packed in a hash.
Now takes 2 operands and pushes multiple entries to an array.
MRB_WORD_BOXING now packs floating-point numbers in the word, if the size of mrb_float is equal or smaller than the size of mrb_int by default. If the size of mrb_float and mrb_int are same, the last 2 bits in the mrb_float are trimmed and used as flags. If you need full precision, you need to define MRB_WORDBOX_NO_INLINE_FLOAT (formerly MRB_WORDBOX_NO_FLOAT_TRUNCATE) as described above.
Previous NaN boxing packs values in NaN representation, but pointer retrievals are far more frequent than floating-point number references. So we add constant offset to NaN representation to clear higher bits of pointer representation. This representation is called "Favor Pointer" NaN Boxing.
Also, previous NaN boxing limit the size of mrb_int to 4 bytes (32 bits) to fit in NaN values. Now we allocate integer values in the heap, if the value does not fit in the 32 bit range, just like we did in Word Boxing.
The code generator was updated to reduce the number of instructions, e.g.
will be interpreted as
In addition, we have improved peephole optimizations, for example:
to
For better and faster hash values.
Following CVEs are fixed in this release.
Following CVEs do not cause problems in this release. They are fixed in the later release.